Wirelessly controlled heads-up display having solar charging and charge level indication

ABSTRACT

A heads up display apparatus for a vehicle, comprising a wireless transceiver configured to connect and communicate with a device providing information for display, an energy storage device configured to provide energy to the display apparatus, a processor configured receive information from the transceiver and configure the information for display, and a display configured to output the information.

TECHNICAL FIELD

The illustrative embodiments generally relate to a wirelessly controlledheads-up display.

BACKGROUND

Below, a few prior art heads up display systems are described.Additional usage of these systems may be obtained and described from theidentified references below.

U.S. Pat. No. 5,414,439 discloses a motor vehicle that is equipped withan infrared camera for viewing roadway conditions in terms of a thermalimage, and outputs a video signal to a head up display (HUD) whichprojects the camera view to the operator via the windshield or othercombiner to display a virtual image in the operator's field of view. TheHUD is configured to magnify the image to the same size as the visual orreal scene, and compensates for camera and windshield distortion. Thevirtual image is presented above or below the real scene or may besuperimposed on the real scene. A video processor allows selection ofonly the warmest objects for display.

United States Pub. No. 2010/0253602 discloses a substantiallytransparent windscreen head up display that includes one of lightemitting particles or microstructures over a predefined region of thewindscreen permitting luminescent display while permitting visionthrough the windscreen. A method to display a graphic head up instrumentdisplay upon a substantially transparent windscreen head up display of avehicle includes monitoring operation of the vehicle, monitoring anoperator-defined configuration of the graphic head up instrumentdisplay, determining the graphic head up instrument display based uponthe operation of the vehicle and the operator-defined configuration ofthe graphic head up instrument display, and displaying the graphic headup instrument display upon the substantially transparent windscreen headup display.

United States Pub. No. 2010/0253918 discloses a method to display aninfotainment graphic upon a surface within a vehicle includes monitoringa source of infotainment content. The method also includes determiningthe infotainment graphic based upon monitoring the source ofinfotainment content, and displaying the infotainment graphic upon thesurface including a material reactive to display graphics in response toan excitation projector, wherein the excitation projector includes anultraviolet projector.

SUMMARY OF THE INVENTION

A first illustrative embodiment describes a heads up display apparatusfor a vehicle, comprising a wireless transceiver configured to connectand communicate with a device providing information for display, anenergy storage device configured to provide energy to the displayapparatus, a processor configured receive information from thetransceiver and configure the information for display, and a displayconfigured to output the information

A second illustrative embodiment describes a non-transitory computerreadable storage media storing instructions that, when executed by aprocessor associated with a heads up display (HUD), causes the processorto receive power from an energy storage device, operate an applicationprogram interface to communicate with a device, receive data from atransceiver connected to the device, configure the data into informationfor outputting on a display, and send instructions to the display tooutput the information.

A third illustrative embodiment describes a method for displayinginformation on a heads up display (HUD), comprising generating energy tocharge an energy storage device located within the HUD, utilizing atransceiver to connect and communicate with a device, processing datarequest from the device, wherein the data request includes informationto output on the HUD, and outputting the information on a display

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an illustrative example of a block topology of a wirelessheads-up display.

FIG. 2 shows an illustrative example of a block topology of a wirelessheads-up display.

FIG. 3 depicts an illustrative flow chart of a wireless heads up displayinteracting with a nomadic device or vehicle computer system.

FIG. 4 depicts an illustrative flow chart of a vehicle computer systeminteracting with the nomadic device.

FIG. 5 depicts an illustrative example of output from the HUD that maybe displayed on a semi-transparent or transparent material.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

As required, detailed embodiments of the present invention are disclosedherein; however, it is to be understood that the disclosed embodimentsare merely exemplary of the invention that may be embodied in variousand alternative forms. The figures are not necessarily to scale; somefeatures may be exaggerated or minimized to show details of particularcomponents. Therefore, specific structural and functional detailsdisclosed herein are not to be interpreted as limiting, but merely as arepresentative basis for teaching one skilled in the art to variouslyemploy the present invention.

The invention now will be described more fully hereinafter withreference to the accompanying drawings, in which illustrativeembodiments of the invention are shown. This invention, may however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Like numbers refer to elementsthroughout. As used herein the term “and/or” includes any and allcombinations of one or more of the associated listed items.

The processes described illustratively herein can be implemented ascomputer code stored on a machine readable storage medium and executedby a processor. Storage medium include, but are not limited to, HDD,CDs, DVDs, RAM, ROM, flash drives, or any other suitable storage medium.

FIG. 1 illustrates an illustrative example of a block topology of awireless heads-up display in an automobile. The heads up display (HUD)may be utilized in a car, truck, motor-home, airplane, boat, or anyvehicle of the like. The HUD apparatus 101 may be wireless and movefreely along the dashboard or other surface. Alternatively, the HUD mayalso be configured to be placed in a distinct area of a vehicle orcontain adhesive material to be semi-permanently stored along a surface.The HUD may be used anywhere the display is capable of emitting outputon a transparent or semi-transparent display, however, it may bebeneficial to allow the HUD to be displayed in the driver's peripheralarea to allow the driver to view the information output by the HUD whilemaintaining concentration on the road and other objects ahead of thevehicle.

The HUD 101 may communicate with a vehicle multimedia system 103, aninstrument cluster 105, or any other vehicle computing system or anyconsumer electronic device 104. The HUD may communicate wirelessly 109with the vehicle multimedia system 103 to exchange data and otherinformation. The HUD may also communicate wirelessly 107 with theinstrument cluster to exchange data or information with the instrumentcluster. Multiple devices or systems may be in communication with theHUD to retrieve data or information for outputting to a user. The HUD ordevices connected to the HUD may be in communication with off-boardservers and other sources to obtain dynamic content, such as but notlimited to, traffic information, weather information, vehicleinformation, driver information, or any other data that may be stored onan off-board server.

The HUD may also be completely self-powered by utilizing differentmethods of charging, such as but not limited to harvesting photonicenergy, inductive charging, thermoelectric energy, a hybrid solar panel,etc. to charge a battery, or in one of many alternatives, store in acapacitor. For example, in one illustrative embodiment, the HUD mayutilize a solar panel to charge a battery or capacitor to power the HUD.This may allow the HUD to be completely wireless. The placement of theHUD on a vehicle's dashboard near the windshield may allow for the HUDto be charged through solar cell technology due to the solar energyavailable on the dashboard. In another non-limiting example, the HUD mayharvest thermal energy based on the interior temperature of the vehicle.In another alternative embodiment, the HUD may be capable of beingplugged into an electrical outlet to charge, similar to consumerelectronic devices like a mobile phone or MP3 player. In yet anotherembodiment, inductive charging may be utilized by utilizing inductivecoupling through induction coils. The vehicle dashboard or alternatearea may include a inductive charging pad to provide inductive chargingto the HUD. It should also be noted that an alternative embodiment mayinclude a HUD that is integrated in the vehicle dash and may beconnecting to the vehicle power supply in order to run.

The HUD may display a heads-up image 111 on the windshield 113 uponreceiving data and other information from the various processors incommunication with the HUD. The HUD may output the display in a numberof ways, such as utilizing one or two lines displays, simple ledgraphics, or complex images. The data, information, or images may varydependent on the application. The HUD may also display multipledifferent images within a relative short period of time to depict ananimation or video of the output.

The HUD allows a transparent or semi-transparent display to present datawithout requiring the users to look away from their typical viewpoints.In the vehicle scenario, it allows a driver to view information whilebeing able to maintain focus on the road, rather than traditionaldisplay areas, such as the instrument cluster or center stack.Traditional areas like the instrument cluster and center stack mayrequire a driver to move their eyes from their driving viewpoint. A HUDmay typically contain a projector unit, a combiner, and a videogeneration computer. The HUD may include a convex lens or a concavemirror with LED/LCD at its focus. The HUD may have a processor tointerface between with the HUD and the systems/data to be displayed orgenerated by the imagery and/or symbology to the displayed at theprojection unit.

The user or driver may utilize various interfaces to change or editsettings of the HUD. In one example, the user may utilize switches onthe steering wheel to change settings of the HUD or utilize controls orsettings associated with the vehicle multimedia system 103. A controlinterface that is embedded on another device like the steering wheelswitch or multimedia system may utilize a wired or wireless connectionand two-way communication to edit settings and control of the HUD. TheHUD's control interface may also be implemented on the HUD. The HUD mayalso rely on a vehicle computing system interface to change settings andinterface controls on the HUD.

FIG. 2 illustrates an illustrative example of a block topology of awireless heads-up display. An illustrative HUD schematic 201 may beutilized in the vehicle to output images or video of relevant data to adriver. The HUD may utilize various resistors, transistors, capacitorsto work in conjunction with the processors, microcontrollers,transceivers, display, and other components utilized in the HUD. The HUDmay contain a universal serial bus (USB) interface 211, to allowinteroperability with outside devices, update software, send data, or tocharge the HUD. In one illustrative example, a user may bring a USBflash drive into the vehicle to update firmware or software on the HUDvia the USB interface 211. Furthermore, the USB interface 211 may allowfor the battery or power source to be charged. Furthermore, the HUD mayallow a connection of other consumer electronic devices, such as but notlimited to, a cell phone, MP3 player, tablet, etc. Furthermore, the USBinterface may provide a power source to the HUD.

The HUD may utilize a lithium ion or lithium ion polymer chargedmanagement controller 213 or any other type of charging module. Thelithium ion polymer charged management controller allows for arechargeable battery 212 or any other type of energy storage device 212to charge. The energy storage device may be connected to the chargingmodule via a pitch connector 214. The lithium ion polymer chargedmanagement controller may allow autonomous power source selectionbetween an input or battery. The lithium ion polymer charged managementcontroller 213 may be connected to a photovoltaic module (e.g. solarpanel such as the PRT-07845) to allow charging. The HUD may also utilizea solar module power pack to connect with a solar panel and charge thebattery.

The HUD may include a low input voltage synchronous boost converter 205to utilize with a power source, such as but not limited to asingle-cell, two-cell, or three-cell alkaline, NiCd or NimH, Li-Ion orLi-polymer battery. It may also be used in fuel cell or solar cellpowered devices. The boost converter may allow for an output voltage tobe greater than the source voltage. The boost converter may be based ona fixed frequency, pulse-width-modulation controller using synchronousrectification to obtain maximum efficiency. The converter or step-upconverter 205 may utilize a “Power Save” mode to maintain a highefficiency over a wide load current range. However, “Power Save” modemay be disabled and may force the converter to operate at a fixedswitching frequency. The converter may also be disabled to minimize anybattery drain.

LEDs 207 may be used to display information to a driver or a user. TheLEDs may receive information from the processor 203 regarding variousvehicle data or information. For example, the LED may utilize images orgraphics to indicate various driver information, such as turndirections, fuel economy, tire pressure, traffic, hands free phoneinformation, caller ID, etc. The illustrative embodiment utilizes fivebright LEDs, however, more or less may be used. The LEDs may be moreadvanced and utilize an alphanumeric or digital display that may bedisplayed to the driver. The LEDS may or may not utilize the traditionalmirrors or lenses that a traditional HUD may utilize. For example, theHUD may utilize the windshield or any semi-transparent material tosimply reflect the light emitted from the LEDs. For example, the LEDsmay be arranged on top of the HUD and reflect off of a windshield backto the driver. With utilizing the reflection of the LEDs, additionalflexibility of the placement and angle of the HUD may be attained. Theadvanced display could utilize one or two lines (or more) and stillutilize a similar form factor as the illustrative embodiment FIG. 1. Asan alternative, an LCD may be utilized to output images as well as videoon the heads up display.

The HUD may also include a Bluetooth transceiver 209 or another wirelessmodule to communicate with other devices. The Bluetooth transceiver 209allows the HUD to wirelessly pair and connect with other devices toexchange data, video, audio, and other information. In one illustrativeembodiment, the Bluetooth transceiver 209 may allow the HUD tocommunicate with a vehicle computing system to retrieve vehicle data.Although a Bluetooth transceiver is utilized in the illustrativeembodiment, other wireless transceivers or receivers may be used, suchas, but not limited to, Wi-Fi, RFID, infrared, etc. The vehicle dataretrieved via the wireless transceiver may be processed by the processor203 of the HUD to display onto the windshield or another substantiallytransparent display.

The HUD may also use an application program interface (API) or anothercommunication protocol to communicate with the device. The HUD's API maybe updated via a software or firmware upgrade utilizing the USB port orother connections, such as but not limited to, Bluetooth, WiFi, and anyother wireless or wired connection. The programmable API may allow theHUD to interact with new applications or modules rather than requiringthe HUD to interact with only a particular set of standard applications.In one illustrative example, the HUD may utilize OpenXC to communicatewith a vehicle or another device. OpenXC may utilize an API thatfacilitates communication between the HUD and the VCS or other devices.The hardware module may be implemented in the HUD to allow access to theOpenXC interface. The OpenXC vehicle interface can allow the HUD to readdata from the vehicle in real-time, such as steering wheel angle, GPSposition, and vehicle speed.

The HUD may also utilize a standard generic API that any application ormodule can use. The API may depend on simply the graphical capabilitiesof the HUD. For example, if the HUD utilizes LEDS, the API may receivemessages to either light up, hold on, or flash any specific or all LEDs.Any application or module that utilizes the API could send the commandsbased on various data types, such as but not limited to fuel economy,cross-traffic warnings, etc.

FIG. 3 depicts an illustrative flow chart of a wireless heads up displayinteracting with a nomadic device or vehicle computer system. The HUDmay interact with a variety of nomadic devices, such as, but not limitedto a cell phone, smart phone, tablet, laptop, MP3 player, portablenavigation device, etc. The HUD may utilize a wireless or wiredconnection to connect 301 with a module or another device. The HUD mayconnect via a Bluetooth connection utilizing a Bluetooth receiver oranother wireless connection.

The HUD may also request data 303 from the device in order to outputinformation on the display. For example, if the HUD is currentlyoperating to display fuel economy information, the HUD may periodicallysend a message to a vehicle computer system (VCS) requesting dataindicating the fuel economy of the vehicle. The HUD may also send datato the VCS indicating errors, low power, or any other message. In onenon-limiting example, the HUD may be below a threshold power supply,such as less than 10% of energy capacity. The HUD may send the VCS amessage or data indicating that the HUD may require additional power inorder to operate. The VCS may then interpret the message to display anerror to the user. In another non-limiting example, the VCS may runself-diagnostic routines and identify an error with a connection orfaulty module. The HUD may send the VCS a message indicating thespecific error for the VCS to interpret and output to the user. The VCSmay display the error on a display screen, instrument panel, or via anaudible message.

Upon sending the data to the device, the HUD may receive the requesteddata 305. Such data may include fuel economy information, turn by turnnavigation information, caller ID or other hands free information, oreven images or videos to be displayed. The HUD may analyze the data todetermine if the appropriate data as sent 307. In some scenarios, theHUD may never receive the requested data. The HUD may timeout based on apredetermined threshold time if no data is received by the device. Inanother scenario, the HUD may instead receive data with an error orcorrupted data. The HUD may request the same or different data 303 ifthe data is not sufficient.

The HUD may also receive data or a message from the device to displaycertain information 309 on the HUD. For example, the VCS may receive aphone call through a Bluetooth enable mobile phone. The VCS may send amessage requesting the phone number or caller ID information of theincoming call to be displayed on the HUD. The HUD is capable of two-waycommunication with devices; therefore, the HUD may maintain constantcommunication with the other devices to exchange and output data.

The HUD may analyze the request 311 to determine if it is appropriate todisplay the information on the HUD. In certain scenarios, the HUD maychoose to ignore or reject the request to display information based onthe importance of certain information already displayed on the HUD. Inother scenarios, the data sent from the device may not be operable onthe VCS. The VCS may send data or a message to the device 315 indicatingthat the message could not be displayed or interpreted. The HUD maydisplay output based on the message indicating an error to the user.

The HUD may then aggregate all or some of the data 317 to prepare foroutput on the HUD's display. Aggregation of the data may includeprocessing the data with other retrieved data to output a new data setor particular data set. The output may use various displays, such as butno limited to a alphanumeric LCD, LED, The HUD may be able to determinewhich output is prioritized based on the incoming data set. For example,if an emergency warning (e.g. low fuel) is sent from the VCS with amessage bit indicating a high priority, the HUD may display theemergency warning indicator rather than other output such as fueleconomy.

Although exemplary processes and methods are shown herein, it isunderstood that these are for illustrative purposes only. One ofordinary skill would understand that the steps thereof could beperformed in any suitable order to produce the desired results. Further,one of ordinary skill would understand that some and/or all of the stepscould be replaced by similar processes that produce similar resultsand/or removed if not necessary to produce the desired results inaccordance with the illustrative embodiments. For example, in anon-limiting scenario, the HUD may receive data from the device 305 andsimply output the information based on the data 319, eliminating anyother steps disclosed in the illustrative embodiment of FIG. 3. In thealternative and contrary to the illustrative embodiment of FIG. 3, theHUD may receive a request to display info 309 from a device, prior tosending data to the device 303.

FIG. 4 depicts an illustrative flow chart of a vehicle computer systeminteracting with the nomadic device. The vehicle computer system (VCS)may include, but is not limited to, the vehicle multimedia system andcomponents or devices connected to the vehicle multimedia system,navigation system, an instrument panel, engine control unit, tirepressure monitor, off-board servers, etc. The VCS may connect with theHUD 401 utilizing both a wireless or wired connection. The VCS mayutilize different protocols or APIs to facilitate communication with theHUD.

The VCS may receive a request from the HUD 403 to retrieve data from thevehicle. The HUD may wish to retrieve data indicative of audioinformation (e.g. song, artist, track, title), fuel economy, tirepressure, navigation directions/guidance, traffic, weather, fuel,emergency warnings, etc. The VCS may also be able to retrieve data fromoff-board servers to output information on the HUD.

The VCS may determine if the request from the HUD is acceptable 405. Insome scenarios, the HUD may send a request for data that is unavailablefor retrieval from the VCS. The VCS may send an error message to the HUDindicating the type of error. Furthermore, the data request may notconform to the protocol or API utilized to facilitate communication withthe HUD and VCS. The VCS may not respond to certain data requests andsimply ignore the request. The HUD may be required to timeout anyrequest that does not render a response. In some scenarios, a requestthat is unacceptable may require the HUD to wait and receive anotherrequest that is acceptable. The VCS may also determine that the requestis acceptable and begin to process the request by initiatingcommunication to the relevant modules.

The VCS may begin to collect relevant data 407 when the request isreceived and deemed acceptable. The VCS may collect all relevant datathat is both on-board the vehicle and off-board the vehicle. On-boarddata may include auxiliary or peripheral devices that are not alwaysconnected to the VCS bus or infrastructure. The VCS may requestdifferent modules or processors to send specific data based on therequest. The VCS may be capable of collecting all data to the differentdevices/modules or utilize different devices/modules to facilitate incollection of data.

The VCS may send data 409 to the HUD based on the request. In certainscenarios, the VCS may send all the applicable data to the HUD for theHUD to process and display. In other scenarios the VCS may send only aspecific portion of the data set requested to the HUD. And in anotherscenario, the VCS may send an error message or some other data that wasnot requested to the HUD. An error message may allow the HUD tointerpret the problem in the initial request.

FIG. 5 depicts an illustrative example of output from the HUD that maybe displayed on a semi-transparent or transparent material. The outputfrom the HUD may be displayed on semi-transparent or transparentmaterial 501 such as, but not limited to, the windshield or rear window.The output may be a variety of colors or schemes.

In one illustrative embodiment, the output of the HUD may utilize aborder 503 to allow the driver to understand the region in which the HUDmay output information on the semitransparent material. The border mayalso allow the driver to calibrate placement of the HUD in a region thatis indicative of the driver's peripheral vision when driving.

Furthermore, the HUD may utilize the LEDs to output lines 505 toindicate different information. For example, the output may besuggestive of the driver's fuel economy. In one illustrative embodiment,the HUD may display more lines 505 to indicate the driver's fuel economyis being maximized. In another alternative embodiment, the HUD maydisplay no lines or only a few lines 505 to indicate that the driver isdriving aggressively and not optimizing the vehicle's fuel economy. Asdescribed within the specification, many alternatives exist to displaydifferent information to the driver. For example, the LEDs may bedisplayed in a straight line, but the LEDS may be arranged in any otherpattern.

The processes, methods, or algorithms disclosed herein can bedeliverable to/implemented by a processing device, controller, orcomputer, which can include any existing programmable electronic controlunit or dedicated electronic control unit. Similarly, the processes,methods, or algorithms can be stored as data and instructions executableby a controller or computer in many forms including, but not limited to,information permanently stored on non-writable storage media such as ROMdevices and information alterably stored on writeable storage media suchas floppy disks, magnetic tapes, CDs, RAM devices, and other magneticand optical media. The processes, methods, or algorithms can also beimplemented in a software executable object. Alternatively, theprocesses, methods, or algorithms can be embodied in whole or in partusing suitable hardware components, such as Application SpecificIntegrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs),state machines, controllers or other hardware components or devices, ora combination of hardware, software and firmware components.

While exemplary embodiments are described above, it is not intended thatthese embodiments describe all possible forms encompassed by the claims.The words used in the specification are words of description rather thanlimitation, and it is understood that various changes can be madewithout departing from the spirit and scope of the disclosure. Aspreviously described, the features of various embodiments can becombined to form further embodiments of the invention that may not beexplicitly described or illustrated. While various embodiments couldhave been described as providing advantages or being preferred overother embodiments or prior art implementations with respect to one ormore desired characteristics, those of ordinary skill in the artrecognize that one or more features or characteristics can becompromised to achieve desired overall system attributes, which dependon the specific application and implementation. These attributes caninclude, but are not limited to cost, strength, durability, life cyclecost, marketability, appearance, packaging, size, serviceability,weight, manufacturability, ease of assembly, etc. As such, embodimentsdescribed as less desirable than other embodiments or prior artimplementations with respect to one or more characteristics are notoutside the scope of the disclosure and can be desirable for particularapplications.

What is claimed is:
 1. A computer-implemented method for displayinginformation on a heads up display (HUD), comprising: charging with asolar panel an energy storage device located within the HUD; utilizing awireless transceiver to send vehicle information to a vehicle computersystem (VCS) related to a charge-level status of the energy storagedevice; and outputting the charge-level status in a heads-up manner of avehicle windshield, and a VCS display.
 2. A computer-implemented methodfor displaying information on the heads up display (HUD) of claim 1,wherein the HUD includes an inductive coil.
 3. A computer-implementedmethod for displaying information on the heads up display (HUD) of claim1, further comprising sending a message to the vehicle computer systemutilizing the wireless transceiver, the message indicating a low-energysupply of the HUD when the energy storage device is below a thresholdamount of energy.
 4. A computer-implemented method for displayinginformation on the heads up display (HUD) of claim 1, further comprisingupdating software of the HUD utilizing an application program interface.5. A computer-implemented method for displaying information on the headsup display (HUD) of claim 1, wherein the VCS includes an instrumentpanel.
 6. A computer-implemented method for displaying information onthe heads up display (HUD) of claim 1, wherein the VCS includes avehicle in communication with a nomadic device.
 7. Acomputer-implemented method for displaying information on the heads updisplay (HUD) of claim 1, wherein the energy storage device is abattery, capacitor, or super capacitor.
 8. A heads up display (HUD),comprising: an energy storage device configured to power the HUD andcharge using a solar panel; a wireless transceiver configured to sendvehicle information to a vehicle computer system (VCS) related to acharge-level status of the energy storage device; and a processorconfigured to output the charge-level status in a heads-up manner of avehicle windshield.